Updating dimensions for health plan budgeting

To implement health plan budgeting in your organization, start by making the following changes to the following dimensions:

LOCATION

The LOCATION dimension contains all of the physical locations that have been billed within the organization and is used for monthly reporting and provider-level budgeting. This information is also used for the Axiom Budgeting Health Plan product.

The following table lists all of the options available in this dimension table:

Column Description
LOCATION The LOCATION used in Axiom Budgeting. This must be an alpha code (i.e. WestClinic). Default should be used as the Location code if this dimension is not being used.
Description Identifies the LOCATION description to be used for budgeting and reporting.
KHABgtCode Used for combining accounts together during budget plan file creation. If there are historical values for two accounts that you want to budget as one combined account, list the surviving account number on both lines. If not combining accounts, this value should match value in the LOCATION column. The default value is NA.
KHAInt

Currently no needed for health plan budgeting so the default is NA.

INSCODE

The INSCODE dimension stores information for the insurance/health product plans offered by your organization. This information is used to manage and configure the plans included in related driver tables and in the Health Plan Operations utility. Similar to other dimension tables like ACCT, there are column structures to control what insurance plans will be allowed to interface to the HealthPlan tab and at what level of rollup, if any.

IMPORTANT: Use caution when using multi-layer mapping of the plan codes.

The following table lists all of the options available in this dimension table:

Column Description
INSCODE The short name or code your organization uses to represent the insurance/health plan product.
Description The long description of the insurance/health plan.
InsCode.BgtCode

The code used to group the insurance/health plan products together. For example, grouping all commercial or FFS plans.
KHAInt

Specify whether to include the insurance product in the list of available plans in the Health Plan Operations utility. Enter one of the following:

NOTE: The system will allow you to enter any text into this field, however, it only recognizes HealthPlan as the way to add the plan to the interface

  • HealthPlan - Enter this option to include the product in the list of available plans.

  • NA - Enter this option to remove the product from the list of available plans.

    NOTE: The system will retain historical information for plans removed from the list.

DATATYPE

The DATATYPE dimension for health plan budgeting purposes is used to load configurable categories for revenues and expenses. Use the Axiom provided default for members. Data imported or entered into the data tables will need to include a valid data type from this table.

NOTE: Version 1 DATATYPE dimension permits DATATYPE.DataType='HP_Members' and DATATYPE.BudgetType IN ('HP_Expense','HP_Revenue') - supplied by default data (i.e. one HP_Members DataType and multiple versions of Revenue and Expense).

The following table lists all of the options available in this dimension table:

Column Description
DATATYPE

The DATATYPE used in Axiom Budgeting and Performance Reporting. This must be an alpha code.

  • HP_Members - This is a required default for members data.
  • HP_Revenue - This is a recommended default for revenue, but you may use other codes. For example, other types of revenue may be desired to load and recognized as a separate revenue line item. (i.e. HP_Revenue1, HP_Revenue2).
  • HP_Revenue - This is a recommended default for revenue, but you may use other codes. For example, other types of revenue may be desired to load and recognized as a separate revenue line item. (i.e. HP_Revenue1, HP_Revenue2).
Description Identifies the description to be use for budgeting and reporting.
BudgetType

Used in related driver tables and in the Health Plan Operations utility. Valid codes will typically be what was used in the Datatype column, however these can be used as a mapping code similar to how KHABgtCode is used in other dimensions. For example, if there are codes used in DataType for Revenue1, Revenue2, and so on but the desired configuration is to map Revenue2 to Revenue1, this column would be used for the mapping.

  • HP_Members - This is a required default for members data.
  • HP_Revenue - This is a recommended default for revenue, but you may use other codes. For example, other types of revenue may be desired to load and recognized as a separate revenue line item. (i.e. HP_Revenue1, HP_Revenue2).
  • HP_DrugME - This is a recommended default for Drug Medical Expense, but you may use other codes.
  • HP_HospME - This is a recommended default for Hospital Medical Expense, but you may use other codes.
  • HP_OutPTME - This is a recommended default for OutPatient Medical Expense, but you may use other codes.
KHAInt

Used to identify which Datatype categories to use in the related driver tables and in the Health Plan Operations utility. Valid entries include the following:

  • HealthPlan - Use this code to include the data type.

  • NA - Use this code to exclude the data type.

    NOTE: You may have data you want to record in the actual tables but not necessarily include them for planning purposes.